@baby-Onioneer try starting in safe mode then deleting /etc/config/wireless and reboot.

Your information is very interesting. Thank you for sharing

Hello @Lazar-Demin I tried eveything, I just compiled openwrt18.06 and everything is fine now. Bests

You wrote: Omega2+, probably 0.1.10 b160 ... [ 28.551976] device eth0.1 entered promiscuous mode [ 28.556855] device eth0 entered promiscuous mode [ 28.588837] br-wlan: port 1(eth0.1) entered forwarding state [ 28.594681] br-wlan: port 1(eth0.1) entered forwarding state [ 30.588807] br-wlan: port 1(eth0.1) entered forwarding state [ 32.028929] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: 8701d944 [ 32.028929] [ 32.042988] Rebooting in 3 seconds.. I wrote in Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: ... and a possible reason on 2017-02-05: Omega2+, 0.1.9 b150 (from 0.1.5 b130 to 0.1.9 b150 several FirmWares), without dock / with Arduino Dock 2 ... [ 20.900878] device eth0.1 entered promiscuous mode [ 20.905758] device eth0 entered promiscuous mode [ 20.940478] br-wlan: port 1(eth0.1) entered forwarding state [ 20.946310] br-wlan: port 1(eth0.1) entered forwarding state [ 22.939289] br-wlan: port 1(eth0.1) entered forwarding state [ 24.809528] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: 8701d944 [ 24.809528] [ 24.823293] Rebooting in 3 seconds.. This Kernel panic is a known bug of the closed source MediaTek WiFi driver. Now we know it can not manage if there is a WiFi AP in the neighborhood with some Unicode character in its SSID. Onion @administrators deeply kept silent about this bug. It seems Onion's new WARP CORE driver (also closed source ???) can manage this situation. Unfortunately Onion @administrators do not say too much about this bug feature (as usual ;-). Since you did not mount the microSD card it is absolutely invisible for the bootloader (Das U-Boot). @Denys-Makogon said in [SOLVED] Kernel corrupted after factory reset: @György-Farkas kernel was corrupted for sure, that's something I can tell you with honesty. The device was literally dead, only after inserting a microSD card with a new firmware my device was able to update itself and become functional. Well... no one but you should know if this correct (or not

@Lazar-Demin Hello, i'm trying to solve this problem too, can you explain more specifically where the root of the problem is and what modules it affects? I debugged and find in arch/mips/mm/dma-default.c struct dma_map_ops what consist NULL, do u fix it?

I also wanted to build my own firmware, but this seem not to work, atleast if you want a working wifi connection. What i did is made my own openWrt package. The only problem you got, is you can't remove anything from the build just add it.

@Sycol said in Kernel Panic! No Working init found.: I ran the firmware update from the webapp for my 2+. It bricked. I've noticed that my problem is with the kernel.Ive tried with this http://community.onion.io/topic/1154/omega-2-usb-firmware-install-after-brick-resolved but i cant even get the menu with the reset up. Try this way please: power OFF your Omega2+ press and hold down the Reset button (the momentary push button between the FW_RST pin and the +3.3V) switch the Omega's power ON and after this you should see the UBoot menu on the serial console... Good luck!

@zal-to there are other builds you can use, but you would know that if you cared about finding solutions. btw, there is a new wifi driver under development by onion devs.

@György-Farkas @José-Luis-Cánovas Thanks! Worked!

Just adding myself to the message chain as I also would like to be able to run openvpn, but I don't really want to jump through all the hoops to compile kernels or the openvpn if it's all going to get broken by an Onion update. I would just rather opkg it and have it run

@György-Farkas I created a network with SSID 하이네켄인증포어러2.4G and got the same behavior. I think that the last build solve this. Now I'm running LEDE on my board.

If you're experiencing this same issue in 2020, read on: Root Cause This kernel panic issue was caused by the WiFi driver used in firmware versions 0.1.x Resolution Upgrading the Omega's firmware will resolve this issue. All firmware released March 2018 and later (version 0.2.0 and up) use a completely overhauled and much more stable wifi driver. Use the bootloader and web recovery mode to install the latest firmware. See this guide for more details: http://docs.onion.io/omega2-docs/Firmware-Flashing-Web-Recovery.html

Hi I am getting the index of / console error. When I make 192.168.3.1 it gives this error and it is not an IP conflict problem. Why do I get this error? How do we fix it? I'm waiting for your help